This update corrects several reported problems in AppMaker 1.5 and supports MacApp 3.0 final. (AppMaker 1.5 supported MacApp 3.0B3.)
Procedural
----------
When generating code for a window that had no scroll bars or only one scroll bar, AppMaker sometimes displayed a "%cntlID% undefined" alert and generated incorrect code.
Code generated in C for a list in a window did not compile because it referenced "info". It now references "cur".
EventLoop:Initialize: Changed code to test for the presence of Gestalt. The old code worked until a recent version of MPW removed the declaration of the trap whose existence we were testing.
THINK Pascal generated code: Added {$I-} to disable THINK Pascal's automatic toolbox initialization. (The AppMaker library itself initializes the toolbox.)
TCL
---
C library: LabeledGroup: added a typecast from StringHandle to Handle to avoid a compiler warning if strict prototype checking is turned on.
Code generated in Pascal for a popup menu did not compile because it had C code that should have been Pascal code.
Converting an old-style (DITL) dialog to pane resources now translates an edit text field to CDialogText instead of CEditText.
Code generated for CPanorama, CPicture, and CStaticText in a scroll pane now does an InstallPanorama.
MacApp
-------
MacApp 2, library: renamed TCustom to TCustomCntl to reduce name conflicts. (The Demo has a dialog named TCustom.) We had already made this change for MacApp 3; we forgot to make it for MacApp 2.
'view' resources weren't getting class names for dialog views. As a result, the generated code for the dialog view subclass was not executed.
'view' resources weren't getting class names for AppMaker's custom classes (e.g. picture controls). This caused various runtime errors bcause MacApp didn't recognize the signatures (e.g. pChk) for these classes.
Resizing a TScroller which had both scroll bars would mess up the size and position of the horizontal scroll bar.
All radio buttons were set on. Now only the first radio button in a cluster is set on.
MacApp 3 code generated for a Font menu now does MAGetMenu instead of GetMHandle. The old code stopped working after one of the many Beta changes to MacApp. The new code should always work.
A new TTEView resource was initialized to autoWrap off. It is now on.
MacApp "prefers" that some menu IDs be less than 128. AppMaker was creating hierarchical menus with IDs >= 128. We changed hierarchical menus to have the next available ID unless that ID is greater than 235.
All
---
On SE-class machines, when generating code, AppMaker could crash with the stack overflowing into the heap. We've increased the stack size.
Big non-purgeable resources were eating up AppMaker's partition. Symptoms included pictures displayed as gray rectangles. Now AppMaker better manages its own memory by temporarily purging resources.
Newly-created documents had Revert enabled. Choosing Revert deleted all of the standard resources. Now the new document is implicitly saved.
Deleting menu items left garbage in the resource beyond the logical end of the menu. The menu resource worked okay; the only symptom was that ResEdit complained about extra data beyond the end of the resource. This is now fixed in AppMaker's Menu Editor and in Stationery documents' Edit menu.
When generating ResourceDefs for a resource type that had some named resources and some unnamed resources, AppMaker sometimes generated garbage characters. This was reported only for MacApp 3, and only when running on a machine with more than 8Mb of memory in 32-bit mode. We couldn't reproduce this problem to fix it, so we programmed around it by modifying stationery files to have resources all named or all unnamed.
